Outbound INVENTORY EDI processes

An INVENTORY EDI session is an outbound EDI session that uses the INVENTORY EDI class. You can use an INVENTORY EDI session to extract unit data for all of the units in a complex or facility into an XML file to send to another system, such as a mainframe system. This enables you to synchronize unit data in N4 with another system.

This is not a standard EDI message, therefore an EDI message type for the INVENTORY EDI class does not exist and N4 does not require a mapping file in the EDI session. N4 formats the extracted XML file according to the snx.xsd schema file. For more information on SNX, see SNX Importer form.

By default, the extracted XML file contains each unit facility visit that is visible in XPS for the current complex. In addition, you can define session criteria in the EDI Session form (on page 1) to restrict the data included in the extract EDI message. For example, if you only want to extract export containers for a specific facility you can define session criteria to limit the extracted data to the specified facility and category.

N4 does not extract incremental changes; each extract contains all of the unit facility visit data that is visible in XPS for the current complex and that satisfies the session criteria in the EDI session, if specified. A typical output XML file contains several thousand records.

To manually extract an INVENTORY EDI session, see EDI Session form (on page 1). In addition, you can add an EDI job to schedule automatic extracts. For more information, see EDI Job form (on page 1).

When successful, N4 sends the XML file according to the EDI mailbox (on page 1) specified in the EDI session.

You can also use the Actions Export SNX File option in some list views to export data into an XML file. For more information, see Export SNX File.